chore: migrate from GitVersion to release-please#446
Conversation
- Add release-please config, manifest (seeded at 2.8.0), and workflow. - Disable legacy create-release.yml to prevent double-tagging. - Remove GitVersion setup/execute steps and tag-push from .azuredevops/pipelines/github-push.yml. - Delete unused .azdo/pipelines/github-push.yml duplicate. - GitVersion.yml is intentionally left in place; full deletion is tracked as follow-on work. 🤖 - Generated by Copilot
6358b99 to
aa306f5
Compare
📚 Documentation Health ReportGenerated on: 2026-04-25 22:37:58 UTC 📈 Documentation Statistics
🏗️ Three-Tree Architecture Status
🔍 Quality Metrics
This report is automatically generated by the Documentation Automation workflow. |
📚 Documentation Health ReportGenerated on: 2026-04-26 02:41:49 UTC 📈 Documentation Statistics
🏗️ Three-Tree Architecture Status
🔍 Quality Metrics
This report is automatically generated by the Documentation Automation workflow. |
📚 Documentation Health ReportGenerated on: 2026-04-27 07:04:05 UTC 📈 Documentation Statistics
🏗️ Three-Tree Architecture Status
🔍 Quality Metrics
This report is automatically generated by the Documentation Automation workflow. |
katriendg
left a comment
There was a problem hiding this comment.
✅ Approved — Clean migration from GitVersion to release-please
Well-structured PR. The removal of legacy GitVersion tooling and ADO release-branch-create pipeline is thorough, and the new release-please.yml workflow is correctly configured with SHA-pinned actions and least-privilege permissions.
Items to address before merge
RI-01 (Medium) — Stale create-release.yml references in troubleshooting section (not inline — lines are outside the diff)
docs/build-cicd/release-workflow.md still references create-release.yml in four places within the troubleshooting section (around original lines ~692, ~870, ~915, ~1044). Since that workflow was renamed to .disabled, commands like gh workflow run create-release.yml and gh run list --workflow=create-release.yml will fail. These should be updated to release-please.yml with appropriate arguments.
RI-02, RI-03, RI-04 — See inline comments.
Verified — No Regressions
release-please-actionSHA verified against v4.4.1 tag ✅- Workflow permissions correctly scoped ✅
release-please-config.jsonand.release-please-manifest.jsoncorrectly configured ✅- All GitVersion references removed from active config and pipeline files ✅
- ADO
github-push.ymlproperly trimmed of Versioning job ✅ - All deleted files have cross-references cleaned in ADO docs ✅
workflow_dispatch-only trigger is intentional for rollout safety ✅
📚 Documentation Health ReportGenerated on: 2026-04-29 16:28:24 UTC 📈 Documentation Statistics
🏗️ Three-Tree Architecture Status
🔍 Quality Metrics
This report is automatically generated by the Documentation Automation workflow. |
- update create-github-app-token comment to v3.1.1 (RI-02) - migrate release-workflow.md references from create-release.yml to release-please.yml (RI-01) - update mermaid diagram and narrative to remove Release Review Branch step (RI-03) - bump ms.date to 2025-11-12 (RI-04) 📝 - Generated by Copilot
📚 Documentation Health ReportGenerated on: 2026-04-30 03:53:51 UTC 📈 Documentation Statistics
🏗️ Three-Tree Architecture Status
🔍 Quality Metrics
This report is automatically generated by the Documentation Automation workflow. |
|
@katriendg Re RI-01 (stale
Grep verified zero remaining |
📚 Documentation Health ReportGenerated on: 2026-04-30 05:21:36 UTC 📈 Documentation Statistics
🏗️ Three-Tree Architecture Status
🔍 Quality Metrics
This report is automatically generated by the Documentation Automation workflow. |
Pull Request
Description
Migrate GitHub-side release management from GitVersion + the custom
create-releaseworkflow to release-please-action v4.4.1 using thesimplerelease type with a manifest-driven configuration. The new workflow isworkflow_dispatchonly (no auto-trigger on push) so releases remain explicitly gated.This PR also removes the parallel Azure DevOps release-branch automation that was tightly coupled to GitVersion, since release management now runs from GitHub. The Azure DevOps
github-pushmirror pipeline is retained but trimmed of GitVersion references.Net change: 17 files, +148 / -1364.
Related Issue
Relates to WI-01 (replace GitVersion with release-please on GitHub side).
Type of Change
Implementation Details
Added
.github/workflows/release-please.yml—workflow_dispatch-only workflow invokinggoogleapis/release-please-action@v4.4.1(pinned).release-please-config.json—simplerelease type, single root package..release-please-manifest.json— pinned to current version2.8.0.Disabled (kept on disk, renamed so GitHub no longer schedules it)
.github/workflows/create-release.yml→.github/workflows/create-release.yml.disabledDeleted
GitVersion.yml(root).azuredevops/pipelines/release-branch-create.yml.azuredevops/docs/release-branch-create.md.azdo/pipelines/github-push.yml(superseded by.azuredevops/pipelines/github-push.yml)Modified (docs + ADO mirror)
docs/build-cicd/release-workflow.md— describes release-please trigger, manifest, and version bump flow.docs/build-cicd/configuration-reference.md— replaces GitVersion config reference with release-please config reference..azuredevops/docs/github-push.md— removes GitVersion language..azuredevops/pipelines/github-push.yml— removes GitVersion variable group and step..azuredevops/README.md— drops the release-branch-create entry..github/copilot-instructions.md— points contributors at release-please instead of GitVersion.Testing Performed
Validation Steps
All validators reported no errors at HEAD
6427d727.Checklist
terraform fmton all Terraform codeterraform validateon all Terraform codeaz bicep formaton all Bicep codeaz bicep buildto validate all Bicep codeTerraform / Bicep / test items are N/A — this PR is JSON + YAML + Markdown only.
Security Review
The diff touches only release tooling configuration and docs. The release-please action is pinned to
v4.4.1. No code paths, identity boundaries, or network resources are changed.Note: a Grype scan of the repo (unrelated to files modified by this PR) reports 4 pre-existing CVEs in dependencies (
go.opentelemetry.io/otel,postcss,uuid,github.com/jackc/pgx/v5). These should be addressed in a separate dependency-bump PR per precedent (#427, #444).Additional Notes
6427d727(up to date withmainatc01b934f).workflow_dispatch-only for this rollout; once verified, a follow-up PR can enable the standardpush: branches: [main]trigger.release-branch-createpipeline is removed because release-branch creation is now handled by release-please's release PR. The ADOgithub-pushmirror remains.Screenshots (if applicable)
N/A — no UI changes.